From: kfraser@localhost.localdomain <kfraser@localhost.localdomain>
Date: Mon, 10 Jul 2006 14:57:56 +0000 (+0100)
Subject: [XEND] Currently a domain's maxmem value is being set with the memory value
X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~15878
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=1a1f70afb8b93d956ddbd8b696a93fec1418d4c7;p=xen.git

[XEND] Currently a domain's maxmem value is being set with the memory value
even if the user specifies maxmem in config.  This patch uses maxmem
value to set maxmem instead of memory.

Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
---

diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py
index b100a7d557..5ded5537b3 100644
--- a/tools/python/xen/xend/XendDomainInfo.py
+++ b/tools/python/xen/xend/XendDomainInfo.py
@@ -1302,9 +1302,11 @@ class XendDomainInfo:
                     cpu = [ int( cpus[v % len(cpus)] ) ]
                     xc.vcpu_setaffinity(self.domid, v, cpu)
 
+            # set domain maxmem in KiB
+            xc.domain_setmaxmem(self.domid, self.info['maxmem'] * 1024)
+
             m = self.image.getDomainMemory(self.info['memory'] * 1024)
             balloon.free(m)
-            xc.domain_setmaxmem(self.domid, m)
 
             init_reservation = self.info['memory'] * 1024
             if os.uname()[4] == 'ia64':